Propagate disable_torch_autograd
to thunderfx's _splitter
#2534
+20
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes somewhat unexpected graph splits in thunderfx path with programs that use
torch.library.custom_op
even when it's manually registered through_register_custom_op
.For example, when there's a
torch.library.custom_op
that's registered to Thunder without backward definition, that custom_op could result in a graph split. This is because splitter only sees input proxiesrequires_grad
--lightning-thunder/thunder/dynamo/utils.py
Lines 312 to 322 in 280c57e
close #2606